Tooling for translations #496
Conversation
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
2 times, most recently
from
b699910 to
19345c8
Compare
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
from
19345c8 to
7bb4651
Compare
Sure, I've just hit the resync button. I think it worked because the integration page now shows a 200 activity. |
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
from
7bb4651 to
309aa24
Compare
|
Sweet - it's building both the english and the chinese version for each PR now. Not quite perfect with the naming, yet: Not sure where we can change that. The second one definitely seems to be built in Chinese, though :) |
Turns out I had to recreate the project on readthedocs to change the "project slug". @steve-chavez could you do me a favor and sync the webhook in the newly created project once more? That should then display it in PRs as |
Done! Got another 200. |
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
2 times, most recently
from
cbb8e7c to
57b331d
Compare
|
Ok, that works. Should be good to merge, but I'll keep this open until @cnyyk has maybe tested it a bit, too, and has something to put in a PR. No need to carry the empty set of |
|
Hello, is there any progress on the Chinese translation project? |
|
Looks like @cnyyk is inactive now. @haowuge Would you like to maintain the chinese docs? I don't recall the procedure here. Maybe Wolfgang can give you more details. |
|
@steve-chavez Hello steve-chavez , my English is not very good, I tried to translate, but the effect is not satisfactory |
|
Hi, @wolfgangwalther @steve-chavez @haowuge, COVID-19 made things chaos, Here's a progress brief (unitl 2023-03-27):
And there're 4 thinngs need to be done:
Working Repo: |
|
Here's the old deadline. I'll make an new plan for this work. |
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
from
57b331d to
43dffc6
Compare
Signed-off-by: Wolfgang Walther <walther@technowledgy.de>
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
2 times, most recently
from
4202454 to
7834a14
Compare
wolfgangwalther
force-pushed
the
chore/translation-tools
branch
from
7834a14 to
8869c17
Compare
|
Because of PostgREST/postgrest#2814, I rebased this PR on latest main, fixed the tooling with new nixpkgs. I will merge this without the empty locale files for zh_CN, which only served as an example. If the tooling needs any improvements, we can work on those later. Just want to get PRs closed here now. |
As #393 recently got some traction, I'm adding support for translations to our build tools.
The main features are:
postgrest-docs-buildwill now update.pofiles' msgids automatically.postgrest-docs-buildandpostgrest-docs-servecan take an argument to build/serve in a specific language@cnyyk could you test the
livereload_docs.pyscript? It should work withoutnix, too. Just call it like./livereload_docs.py zh_CN.I also moved all the actual docs files to a
docs/subfolder to separate the tooling from the content a little bit more.TODO:
.pofiles have been committed. Will do after ci: switch to GitHub Actions #495 is done.SupportEdit:postgrest-docs-spellcheckfor other locales.aspelldoes not support Chinese: http://aspell.net/0.60.7/man-html/Unsupported.html. We might add it later for other languages, once there is a need.Each translation/locale needs another readthedocs project, which will then be set as a "translation project" in their settings. I created a project for simplified chinese as that's currently worked on. @steve-chavez I added you to the project on readthedocs, too - could you please setup the integration / sync the webhook (I'm missing permissions), so that we can test the build process. I'd like to know how PRs are built once we have a translation. I hope to have builds for both languages at the same time.